Peter Knight

That’s brilliant 🤩 Thanks for the skill

WIP Possible approach below. Add a new top-level category — ProcessWire Discussion. It contains community-facing boards that were previously under General support and some new ones. Labels and descriptions are just placeholders. ProcessWire Discussion A place to talk about ProcessWire beyond support — share, discuss and connect with the community. General Discussion — ProcessWire chat that isn’t a support question. Showcase / Case Studies — Have you done something nice with ProcessWire? Share it here. Wishlist & Roadmap — Tell us what you’d like to see in ProcessWire. Module Spotlight — Highlight and discuss notable modules without it being a support question. Business & Freelancing — Pitching PW to clients, agency adoption, pricing and project management. Community & Events — Meet-ups, conferences, PW-related events and community news. Jobs — Post your requirements here if you would like to hire an experienced ProcessWire developer.

That's a pretty wild Module and use of PW. Was the driving motivation a personal project or client?

That's a good point about discussions. Possibly the only downside of forum-only posting is you're losing the SEO benefits. Google sees the .com isn't updated as much, and people researching the platform might not see how alive PW is at the moment.

Looking at this from another angle, I just noticed there are currently 150 guests on the forums (Saturday morning). Even if a percentage of are possibly bots (?), I imagine the conversion rate of casual browser to registered member could be higher with a more casual entry point.

For browsing, I do the same @Ivan Gretsky IE view by recently created etc. That’s 100% not an issue and especially these days where post seem to be much fewer than a few years ago. But just to be clear if @Pete or @ryan are reading, the main issue is for creation of new posts.

I think you should. You can always refine the prompt, seed it with some samples of your own writing style and tweak over time to create an editorial style. In my own case, I wouldn’t consider myself a great writer so I rely heavily on AI but I include this at the top of my blog posts. I always enjoy your posts and Like your writing style. So while I don’t think you need help writing, AI can be brilliant at generating topics you might want to explore further. And you can always review posts before they go live.

Yes, maybe it’s just semantics and labels but it does seem like if a topic is neither support or off topic, its not welcomed or at least has no natural home. I agree Pub and Dev are close. But as Dev itself describes itself as general development and coding discussions and live under a category of Off Topic, it adds to the perceived issue. But I agree that a general bucket called PW topics or whatever will add to moderation issues. Is there a middle ground that doesn’t resort to calling itself General? In my original post, that was just an example label.

A big thanks to @@Mikel for flagging some of the items which form 1.19.1. Uninstall (fixed) The safety check that requires you to opt-in via `$config->MediaHubUninstall` in `site/config.php` was firing a beat too late. By the time the error showed, companion modules and their pages were already partially torn down. 1.19.1 hoists that check into a `hookBefore('Modules::uninstall')` so nothing is touched if the flag is missing. Also tightened companion module cleanup, admin page deletion, and crop-field removal so the whole flow is now atomic: succeeds completely or aborts cleanly. Import (fixed) Importing existing images on a non-MediaHub site (Setup → Media Hub → Import Existing) wasn't generating thumbnails. Bonus: retina `srcset` (1x/2x) and lazy loading on inputfield thumbnails. Icons (aligned) The library and the MediaHub inputfield each have view-mode toggles (grid, proportional or masonry, detail or list), but 1.19.0 used slightly different icon sets between the two surfaces. 1.19.1 aligns them on the same Lucide set. Labels bug (fixed) The new Labels section in 1.19.0 shared structural class names with Collections. This meant Labels were incorrectly displayed on some Collections filters nd menus. Labels and Collections are now strictly separate row types throughout the sidebar. Full changelog 1.19.1 blog post 1.19.1 download

Missed the third developer's input. They said they spend 90% of their day working in Processwire, work solo with no real PW interaction apart from the forums. They often wish they could jump into the forums and share PW stuff without feeling like it needs to be support related or forced into off-topic.

I've been meaning to raise this for a few years, and ironically, anytime I went to highlight it, I didn't know where to post it. Would it be worth adding a General Discussion area under Community Support for ProcessWire-related topics that aren't support questions? The gap I keep running into is topics that are clearly on-topic for PW but don't fit any of the support categories and aren't off-topic enough for the Pub or Dev Talk. Here are three sample posts to illustrate the issue: 1. "How do you pitch ProcessWire to clients who only know WordPress?" - not a support question, not off-topic, not a tutorial 2. "What's your experience of the PW community compared to other CMS communities?" - clearly PW-related but doesn't belong in any support board 3. "I'm seeing more agencies adopt PW in Germany - anyone else noticing regional growth?" - on-topic community discussion with nowhere to land I recently spoke with three PW users, and one told me they don't visit the forums at all because there's nowhere to simply chat about ProcessWire. Another wasn't aware of many of the recent Module developments because module-related content gets buried within Modules rather than somewhere more visible. I suspect both of those things would improve with a single well-placed General Discussion board. Just to recap, I think the boards are structured very well and cater for *most* topics. But has anyone else felt this gap or had posts they couldn't find a home for?

Hey everyone, MediaHub 1.19.0 is ready. That is good news for two reasons: you might find it useful, and you might be too distracted to wonder where 1.18 went. 🙂 Anywho, MH 1.19 has two main areas of improvement: the main MediaHub library screen (for editors) a new read API for galleries at scale (for developers). MediaHub Library changes A) Redesigned sidebar The sidebar has been redesigned and refined, with new shortcut filters at the top B) Favourites Mark any asset as a favourite (site-wide) and filter the library to favourites only. You can favourite from the asset detail page, the tile menu, or by dragging tiles onto Favourites in the sidebar. I am still debating Favourite/unfavourite vs star/unstar for the wording. Open to opinions there. C) Recent See your newest uploads and choose what “recent” means: last 24 hours, last 7 days, and other presets. More flexibility planned here soon. D) Filter breadcrumb type thing When you filter the library, a breadcrumb-style trail shows where you are (for example All Assets › Labels: Dublin). Clear a filter with one click instead of guessing how you narrowed the view. E) Labels If you use Labels for organisation, they are now a first-class shortcut in the sidebar, with counts per label. The section collapses when you do not need it. Drag assets onto a label row to assign in bulk; rename or delete from the row menu. F) Hover info on asset cards Hover over an asset to quickly see the title and filename without turning on Details view or opening the full asset page. This way, you get a really clean Library grid and still benefit from an in-betweeny view. G) Favourites (pt2) You can mark an asset as a favourite from the assets card/panel. Admittedly, 'unfavourite' is a little awkward-sounding. How does it read in German, Austrian, Bulgarian, Irish? I'll find out shortly. I might change this to star/unstar. MediaHub - drag and drop Another gap closed. You can drag and drop assets directly onto a MediaHub field. If you want to disable that function, you can do it on a field-by-field basis. You can also re-order assets as per the native input field. And if you're not a drag-and-drop fan, you can use the buttons instead. The MediaHub button will open your Library. Upload button opens your Finder. Uploads and drag-and-drop currently land new files in the root of the library in the background. I am planning more flexibility there soon. getRaw () API (beta) I'll be straight: I have not fully tested this myself on production sites yet, but I did run it through rigorous automated test scripts, and the performance benefits look promising. There is a more comprehensive write-up in the MediaHub docs. And I want to thank @David Karich for pushing this feature forward and flagging the original limitation in the first instance. Not strictly 1.19 related Search the docs The MediaHub documentation has a new search box in the sidebar Limitations and planned improvements Created a page with the known gaps in MediaHub. This is going to be a living (but rapidly shrinking) list as I move towards MediaHub 1.20.X. Get 1.19: About MediaHub: https://www.peterknight.digital/products/mediahub/ Upgrade to 1.19: https://www.peterknight.digital/downloads/mediahub/ Read the blog: https://www.peterknight.digital/blog/posts/mediahub-1-19-release/ Full changelog: https://www.peterknight.digital/docs/mediahub/v1/changelog/ Cheers 🍻 Peter

Thanks Stefan. It’s really great to hear this. Looking forward to seeing your next site too. 🙂

Update: 2 tester spots remaining. I’m keeping each wave small to give proper attention to feedback and bug reports. More spots will open up soon. Also worth mentioning, a few people have simply gone ahead and purchased without any prompting. Whether that’s a vote of confidence in the module or to lock in the current pricing before 1.20 lands, either way, it means a lot. Thank you. ☺️

Quick update if you've landed here. Media Hub now has its own forum and future updates can be found here.